Anyone knows what these error messages mean?

Hi everyone, i receive constantly the following type error messages from DXL when i compile my program.

utils/ole.inc

utils/attrlist.inc

Lines corresponding to these errors have no meaning, and i cannot get why i am receiving these errors, even if i do something wrong, i cannot determine from where these faults arise.

Thanks in advance for your attention. Kind regards
SystemAdmin - Wed May 27 11:18:46 EDT 2009

Re: Anyone knows what these error messages mean?
SystemAdmin - Wed May 27 11:22:16 EDT 2009

i misclicked on "mark as answered" button.

Re: Anyone knows what these error messages mean?
SystemAdmin - Wed May 27 12:10:23 EDT 2009

What is the actual error message?

Re: Anyone knows what these error messages mean?
SystemAdmin - Thu May 28 03:18:13 EDT 2009

Hi Pekka here are some examples to the error messages that i receive:

-E- DXL: <utils/ole.inc:221> non local variable access (cPropertyVisible)
-E- DXL: <utils/attrlist.inc:47> non local variable access (alAttributes)
-E- DXL: <utils/attrlist.inc:63> non local variable access (alExportList)
-E- DXL: <utils/attrlist.inc:63> non local variable access (alSelectedAttr)
-E- DXL: <utils/attrlist.inc:65> non local variable access (alSelectedAttr)

As I have remarked, for example these numbers indicated next to the error type cannot be line numbers since lines corresponding to these numbers do not have any relevance with the code. Also i searched for the terms printed in paranthesis, at least it is for sure that there are no such named DXL functions.

Thanks one more time for your response.

Re: Anyone knows what these error messages mean?
Tony_Goodman - Thu May 28 06:06:42 EDT 2009

SystemAdmin - Thu May 28 03:18:13 EDT 2009
Hi Pekka here are some examples to the error messages that i receive:

-E- DXL: <utils/ole.inc:221> non local variable access (cPropertyVisible)
-E- DXL: <utils/attrlist.inc:47> non local variable access (alAttributes)
-E- DXL: <utils/attrlist.inc:63> non local variable access (alExportList)
-E- DXL: <utils/attrlist.inc:63> non local variable access (alSelectedAttr)
-E- DXL: <utils/attrlist.inc:65> non local variable access (alSelectedAttr)

As I have remarked, for example these numbers indicated next to the error type cannot be line numbers since lines corresponding to these numbers do not have any relevance with the code. Also i searched for the terms printed in paranthesis, at least it is for sure that there are no such named DXL functions.

Thanks one more time for your response.

You got any nesting in your code that includes these?

I get the following error when I include utils/attrlist.inc
-E- DXL: <utils/attrlist.inc:63> undeclared variable (deleteList_)

I am using DOORS 9.0.

Interestingly, I notice from attrlist that you can omit the ".dxl" extension if you are #inlcuding a dxl file, the following both work:
#include <utils/skipfns.dxl>
#include <utiles/skipfns>

Re: Anyone knows what these error messages mean?
Tony_Goodman - Thu May 28 06:09:53 EDT 2009

This code

void fred()
{
    string s = "hello"
        void sue()
        {
                print s
        }
}

generates this error

-E- DXL: <smartdxl/amg.inc:7> non local variable access (s)
-I- DXL: all done with 1 error and 0 warnings

that is why I suspect you may have some braces around the #include statements?

Re: Anyone knows what these error messages mean?
llandale - Thu May 28 10:09:31 EDT 2009

The *.inc files are routinely encrypted and of course look like garbage in an editor. The line number errors correspond to the unencrypted files; which you don't have access to. Yes, using Windows Explorer to search for variables that are encrypted won't work.

In DXL, sested functions cannot access variables in the parent function; only local variables and those in the Main. This makes nesting functions practically useless, and in any case they are quite confusing.

As Goodman said you are probably issuing that #include statement from within some function, perhaps "If such-and-such then do then #include and do the Telelogic function". Don't know what to do about that, other than make sure the #include statement is in the MAIN.

-Louie

Re: Anyone knows what these error messages mean?
SystemAdmin - Thu May 28 12:15:11 EDT 2009

llandale - Thu May 28 10:09:31 EDT 2009
The *.inc files are routinely encrypted and of course look like garbage in an editor. The line number errors correspond to the unencrypted files; which you don't have access to. Yes, using Windows Explorer to search for variables that are encrypted won't work.

In DXL, sested functions cannot access variables in the parent function; only local variables and those in the Main. This makes nesting functions practically useless, and in any case they are quite confusing.

As Goodman said you are probably issuing that #include statement from within some function, perhaps "If such-and-such then do then #include and do the Telelogic function". Don't know what to do about that, other than make sure the #include statement is in the MAIN.

-Louie

Those inc files mentioned (in the util subdirectory) are not encrypted. The variable names are variables in these files.

Re: Anyone knows what these error messages mean?
llandale - Fri May 29 11:02:46 EDT 2009

SystemAdmin - Thu May 28 12:15:11 EDT 2009
Those inc files mentioned (in the util subdirectory) are not encrypted. The variable names are variables in these files.

Ok, unencrypted. I took a look at the various versions of ole.inc and these variables are indeed used therein, but yes the line numbers don't match up right. Here are some thoughts, perhaps one is useful:

[] Not noticed lately, but noticed in the past that the DXL errors sometimes reported the correct line number but reported the wrong file the line was in. Never figured it out. Perhaps then the file is wrong.
[] Batch mode loads a different set of include files other than startup.dxl, and if you use some stuff normally it may not work in Batch. All my batch programs #include several specific installed files to make them work.
[] Previous comments about #including within a function still apply. Since ole.inc has no actual call to any of its functions, you can put it at the top of your DXL. If it did, its theoretically possible to get around this as follows:
>>Put a 'halt', followed by all these #includes at the bottom of your DXL.
>>Forward declare the functions from within these #include statements -- those that you intend to call -- at the top of your DXL.
>>Call the functions from within your own functions, perhaps DBE callbacks.

Forward Declares look exactly like the standard declares but are NOT followed by a brace "{}" characters; for example:

string DoubleIt(string InString)   // Forward Declare, no {} characters
 
void  DoIt()
{  string In  = "Abc"
   string Out = DoubleIt(In)
   print "Out = " Out "\n"
}
 
string DoubleIt(string InString)
{  print ">> In DoubleIt [" InString "]\n"
   return(InString InString)
}
 
DoIt()

-Louie

Re: Anyone knows what these error messages mean?
SystemAdmin - Mon Jun 01 03:29:43 EDT 2009

I want to thank everyone for their detailed explaination, after reading your answers i figured out that i have been using the nested void functions which might cause this problem, even tough i could not fix the problem at least now i know i am receiving these error messages thanks to you all.